Implementing distributed debug data collection and analysis for a shared adapter in a virtualized system

ABSTRACT

A method, system and computer program product are provided for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as, a Single Root Input/Output Virtualization (SRIOV) adapter in a virtualized system. A predetermined event triggers a base error collection sequence. Adapter driver data is collected and virtual function (VF) device drivers are locked out responsive to triggering the base error collection sequence. Adapter debug data is collected and the adapter is reinitialized including an indication to VF drivers if VF error data is to be collected. The virtual function (VF) device drivers are unlocked allowing the VF device drivers to commence recovery of a respective virtual function (VF).

FIELD OF THE INVENTION

The present invention relates generally to the data processing field, and more particularly, relates to a method, system and computer program product for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as, a Single Root Input/Output Virtualization (SRIOV) adapter in a virtualized system.

DESCRIPTION OF THE RELATED ART

Single root input/output (IO) virtualization (SRIOV) is a PCI standard, providing an adapter technology building block for I/O virtualization within the PCI-Express (PCIe) industry. SRIOV capability is a feature of many new PCIe adapters for Fibre Channel, Ethernet, Infiniband, and Converged Network Adapters (CNA).

The SRIOV adapter has an I/O adapter virtualization architecture that allows a single I/O adapter to be concurrently shared across many different logical partitions. The sharing is done at a physical level, so that each logical partition has access to a slice of the physical adapter. The sharing is accomplished via partitioning the adapter into many different PCI functions, and then distributing access to those functions. The adapter is presented as one or more physical functions (PFs) that control functions, for example used for both configuration and I/O, and a set of virtual functions (VFs), used for I/O and limited configuration, each VF represents a slice of the adapter capacity that can be assigned to a logical partition independently of other VFs. Each logical partition has a device driver for each of the VFs assigned to the logical partition.

With the SRIOV adapter a new problem arises when an error is encountered. The desire is to collect error data when an interesting problem arises, and to capture all error data on the first occurrence of an error, or first failure data capture (FFDC), such that problem recreates are not required. This error data can include items such as an adapter dump, device driver state, PCI function state, system state, and the like. For a shared SRIOV adapter, there are multiple device drivers concurrently running in multiple partitions all talking to the same adapter. Additionally, the error data may be privileged, such that there may be security reasons why a given VF should not have access to the error data for other VFs.

Additionally, error data must be captured judiciously as it is expensive in both size required to save the error data, and the length of time to collect the information. Collecting error data in the absence of an important error is undesired because of this cost. For example, it can lengthen the recovery time and result in an increased period of time where I/O is unavailable causing potential customer impact.

Further, the debug data to be collected is distributed across the system. Relevant data to be captured may reside in the adapter, in a system hypervisor, and in operating system partitions. Additionally, the entity that detected the error may not have access to all of the error data across the system that is relevant to the problem at hand. There is no direct communication channel between the partitions and the hypervisor that can be used to communicate and coordinate the process.

A need exists for an effective mechanism to enable distributed debug data collection and analysis for a hardware I/O adapter or a Single Root Input/Output Virtualization (SRIOV) adapter in a virtualized system. It is desirable that such mechanism enables effective and efficient data collection and analysis operations.

SUMMARY OF THE INVENTION

Principal aspects of the present invention are to provide a method, system and computer program product for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as a Single Root Input/Output Virtualization (SRIOV) adapter, in a virtualized system. Other important aspects of the present invention are to provide such method, system and computer program product substantially without negative effects and that overcome many of the disadvantages of prior art arrangements.

In brief, a method, system and computer program product are provided for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as a Single Root Input/Output Virtualization (SRIOV) adapter, in a virtualized system. A predetermined event triggers a base error collection sequence. Adapter driver data is collected and virtual function (VF) device drivers are locked out responsive to triggering the base error collection sequence. Adapter debug data is collected and the adapter is reinitialized including an indication to VF device drivers if VF error data is to be collected. The virtual function (VF) device drivers are unlocked allowing the VF device drivers to commence recovery of a respective virtual function (VF).

In accordance with features of the invention, a system hypervisor manages data collection from the adapter, and additionally provides the novel in-band indication to the VF device drivers as to whether error data is to be collected and saved.

In accordance with features of the invention, the predetermined event triggering the base error collection sequence includes an adapter driver provided with a system hypervisor detecting one of an internal adapter driver error, a platform error, an adapter error, and an adapter dump present on the adapter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention together with the above and other objects and advantages may best be understood from the following detailed description of the preferred embodiments of the invention illustrated in the drawings, wherein:

FIGS. 1, and 2 illustrates a respective example computer system and example system for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as, a Single Root Input/Output Virtualization (SRIOV) adapter in accordance with the preferred embodiment;

FIGS. 3, and 4 together provide a flow chart illustrating exemplary operations for implementing distributed debug data collection and analysis for the SRIOV adapter in accordance with the preferred embodiment; and

FIG. 5 is a block diagram illustrating a computer program product in accordance with the preferred embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings, which illustrate example embodiments by which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the invention.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In accordance with features of the invention, a method, system and computer program product are provided for implementing distributed debug data collection and analysis for a hardware I/O adapter, such as a Single Root Input/Output Virtualization (SRIOV) adapter, in a virtualized system.

Having reference now to the drawings, in FIG. 1, there is shown an example computer system generally designated by the reference character 100 for implementing distributed debug data collection and analysis for a hardware I/O adapter or Single Root Input/Output Virtualization (SRIOV) adapter 102 in accordance with the preferred embodiment. Computer system 100 includes one or more processors 104, or central processor units (CPUs) 104 (one shown) coupled by an I/O hub or processor host bridge 106 to the Single Root Input/Output Virtualization (SRIOV) adapter or hardware I/O adapter 102.

Computer system 100 includes a memory 108 and one or more logical partitions (LPARs) 110 (one shown) coupled by a system bus 111 to the processor 104 and the processor host bridge 106. Each operating system (OS) 112 resides in its own LPAR 110, with each LPAR allocated a part of a physical processor 104, an entire physical processor, or multiple physical processors from the computer 100. A VF device driver 114 is provided with the logical partition (LPAR) 110. A portion of the memory 108 is allocated to each LPAR 110. Computer system 100 includes a hypervisor 116 including a configuration mechanism 118. The hypervisor 116 is a part of the system firmware and manages the allocation of resources to each operating system 112 and LPAR 110.

As shown, a hardware management console (HMC) 120 used, for example, to manage system functions including logical partition configuration and hardware virtualization, is coupled to the hypervisor 116 via a service processor 122. Computer system 100 includes a physical function (PF) manager or PF adjunct 124 provided with the hypervisor 116. The PF adjunct 124 includes an adapter driver 128 to manage physical functions of the hardware I/O adapter 102. The hypervisor 116 uses the PF adjunct 124, for example, to configure physical functions (PFs) and virtual functions (VFs) of the hardware I/O adapter 102 based on configuration information provided by a system administrator via the hardware management console 120.

As shown, the hardware I/O adapter 102 includes, for example, a first physical function 130, a second physical function 132, a first port 134, and a second port 136. The hypervisor 116 using the PF adjunct 124 configures virtual functions based on the physical functions 130, 132 and associates virtual functions with one or more of the ports 134, 136 of the hardware I/O adapter 102.

For example, a first virtual function, 140, instance 1, and the Mth instance of the first virtual function 142, where M is greater than 1, are associated with the second port 136. As shown, a second virtual function 144, such as the first instance of the second virtual function 144 and the Pth instance of the second virtual function 146, where P is greater than 1, are associated with the first port 134. As shown, multiple instances of an Nth virtual function, where N is greater than 2, such as the first instance of the Nth virtual function 148 is associated with the first port 134 and the Qth instance of the Nth virtual function 150, where Q is greater than 1, is associated with the second port 136.

Each instance of the first virtual function 140, 142, the second virtual function 144, 146, and Nth virtual function 148, 150 are hosted by a physical function, such as one of the first physical function 132, the second physical function 132, and another physical function (not shown).

Each instance of the first virtual function 140, 142, the second virtual function 144, 146, and Nth virtual function 148, 150 includes a respective virtual function identifier (ID), shown as ID 152, ID 154, ID 156, ID 158, ID 160, and ID 162. Each virtual function identifier uniquely identifies a particular virtual function that is hosted by the hardware I/O adapter 102. For example, when a message (not shown) is routed to a particular virtual function, the message includes the identifier associated with the particular virtual function.

Computer system 100 is shown in simplified form sufficient for understanding the present invention. The illustrated computer system 100 is not intended to imply architectural or functional limitations. The present invention can be used with various hardware implementations and systems and various other internal hardware devices.

Referring to FIG. 2, there is shown another example system generally designated by the reference character 200 for implementing distributed debug data collection and analysis for a hardware I/O adapter or Single Root Input/Output Virtualization (SRIOV) adapter 202 in accordance with the preferred embodiment.

System 200 includes a hypervisor 204 or other virtualization intermediary, used to enable multiple logical partitions to access virtual functions provided by hardware that includes the hardware I/O adapter 202. For example, as shown in FIG. 2, the hypervisor 204 is used to enable a first logical partition 206, a second logical partition 208, and an Nth logical partition 210, to access a plurality of virtual functions 212, 214, 216, 218 that are provided by the hardware I/O adapter 202. For example, the hypervisor 204 used a first physical function 220 of the hardware I/O adapter 202 to provide a first instance of a first virtual function 212, a second instance of a first virtual function 214, and an Nth instance of a first virtual function 216 to the logical partitions 204, 206, 210. As shown the hypervisor 204 uses a second physical function 222 of the hardware I/O adapter 202 to provide a second virtual function 218 to the logical partitions 206, 208, 210.

The physical functions 220, 222 advantageously include PCI functions, supporting single root I/O virtualization capabilities. Each of the virtual functions 212, 214, 216, 218 is associated with one of the physical functions 220, 222 and adapted to share one or more physical resources of the hardware I/O adapter 202.

Software functions or modules, such as a physical function (PF) adjunct 224 including an adapter driver 225, is provided with the hypervisor 204 for managing the physical functions 220, 222 and the virtual functions 212, 214, 216, 218. For example, a user may specify a particular configuration and the hypervisor 204 uses the PF adjunct 224 to configure the virtual functions 212, 214, 216, 218 from the physical functions 220, 222.

For example, in operation, the hypervisor 204 with the PF adjunct 224 enables the first virtual function instances 212, 214, 216 from the first physical function 220. The hypervisor 204 with the PF adjunct 224 enables the second virtual function 218 from the second physical function 222. The virtual functions 212, 214, 216, 218 are enabled, for example, based on a user provided configuration. Each of the logical partitions 206, 208, 210 may execute an operating system (not shown) and client applications (not shown).

As shown, the client applications that execute at the logical partitions 206, 208, 210 perform virtual input/output operations and include a respective device driver to directly manage an associated virtual function. For example, a first client application executing at the first logical partition 206 may include a first client VF device driver 226, and a second client application executing at the first logical partition 206 may include a second client VF device driver 228.

As shown, the first client VF device driver 226 accesses the first instance of the first virtual function 212. The second client virtual VF device driver 228 accesses the second virtual function 218. A third client VF device driver 230 executing at the second logical partition 208 accesses the second instance of the first virtual function 214. An Nth client VF device driver 232 executing at the Nth logical partition 210 accesses the Nth instance of the first virtual function 216. An access mechanism 234 and a configuration mechanism 236 are provided with the hypervisor 204 to associate a logical partition with an accessed virtual function. The hypervisor 304 uses the access mechanism 234 to enable logical partitions, such as LPAR 206 to access configuration space associated with one or more of the virtual functions 212, 214, 216, 218.

System 200 is shown in simplified form sufficient for understanding the present invention. The illustrated system 200 is not intended to imply architectural or functional limitations. The present invention can be used with various hardware implementations and systems and various other internal hardware devices.

In accordance with features of the invention, debug data to be collected may reside in the adapter, in the hypervisor, and in the operating system partitions. The hypervisor manages the data collection from the adapter, and provides a novel in-band indication to the partitions as to whether error data is to be collected and saved.

In accordance with features of the invention, a system administrator can temporarily give a partition (managing a VF) the ability to initiate error data collection, a privilege which it would not ordinarily have. Advantages of the invention are: Error data is collected only when necessary. Error data is collected across all partitions, as well as the hypervisor and the adapter. No communication is necessary between the hypervisor and the partitions. Existing function-scope data collection is unaffected. That is, a VF driver can collect data for its function without impacting other functions.

In accordance with features of the invention, a base sequence of actions is taken each time error data collection is invoked. The primary driver of the sequence is the adapter driver, which is resident in the hypervisor. This sequence can be triggered by a predetermined event including several stimuli, such as, a specific request from the HMC (hardware management console), adapter driver detected adapter error, such as a command failure, an internal adapter driver software error, an indication of a platform-detected error, and a detection of an adapter dump present on the adapter, where the adapter can decide to self-dump on internally detected errors.

Referring to FIGS. 3 and 4, there are shown exemplary operations of the processing and logic provided by the hypervisor 130 for implementing distributed debug data collection and analysis for a hardware I/O adapter in accordance with the preferred embodiment.

In FIG. 3, as indicated in a block 300, the adapter driver is request to collect error information, for example, a specific request is provided from the hardware management console (HMC) 120. As indicated in a block 302, the adapter driver detects an internal adapter driver error, such as an internal adapter driver software error. As indicated in a block 304, the adapter driver detects a platform error, an adapter error, such as a command failure, or an adapter dump present on the adapter, where for example, the adapter can decide to self-dump on internally detected errors. The base error collection sequence is triggered responsive to such predetermined triggering event at block 300, 302, or 304.

The base error collection sequence optionally can be initiated by a VF device driver in accordance with a preferred embodiment. Ordinarily a VF device driver does not have the privilege to initiate the data collection process. The key reason is that this is a disruptive process, resulting in temporary I/O disruptions as the process completes. A misbehaving device driver can cause significant system impacts.

In accordance with features of the invention, a VF device driver is enabled to initiate the data collection process and there are important cases where this may be required. One example is to trigger an adapter dump immediately upon some VF-detected condition. This could be necessary since delaying the adapter dump might result in important information being lost due to delays in initiating the recovery. To accommodate the VF device driver being enabled to initiate the data collection process, a new adapter capability has been specified and implemented. This capability is a settable privilege or dump initiation for a given VF. When a VF has been given this privilege, a VF device driver can request the adapter initiate an adapter dump. The VF device driver still cannot collect the dump, for security reasons. This privilege can be dynamically added/removed concurrent with normal VF operations.

For example, a system administrator uses the HMC to give a VF dump privilege, and the HMC communicates this to the adapter driver, for example, at block 300. The adapter driver communicates with the physical adapter to update the VF privileges. Also, for example, when the VF device driver detects a problem for which it would like to generate an adapter dump, the VF device driver queries the adapter to determine if it has the required privilege level. Alternatively, the VF device driver can blindly attempt and fail if not authorized. Also, for example, the VF device driver requests the adapter generate an adapter dump. This dump is presumably close in time to some important event detected by the VF device driver, and the adapter dumps itself. The adapter driver detects, for example, via background health poll the existence of the adapter dump, such as at block 304, which initiates the data collection sequence The VF dump privilege is revoked by the system administrator using the HMC. The HMC notifies the adapter driver, which then updates the VF configuration in the physical adapter.

In FIG. 3, adapter driver data is collected as indicated in a block 306. The VF device drivers are locked out utilizing an enhanced error handling (EEH) functionality of the processing and logic provided by the hypervisor 130; and I/O processor host bridge debug data is collected as indicated in a block 308. Next adapter debug data in the adapter at the time of failure is collected; this includes the register set, as indicated in a block 310. Next, an adapter dump is triggered or generated if one is not already present on the adapter, as indicated in a block 312. The adapter dump is collected or retrieved from the adapter as indicated in a block 314. This possibly may require resets and reinitialization of the adapter, depending on the implementation of the adapter vendor. This adapter dump includes the information on both the adapter and the VFs.

The debug data collected by the adapter driver is sent to the HMC as indicated in a block 316. Next, as indicated in a block 318 the adapter is reinitialized, again, this reprises functionality of enhanced error handling (EEH), and the adapter reinitialization includes an indication to the VF driver as to whether or not error data should be collected. As indicated in a block 320, the VFs are unlocked, allowing the VF device drivers to commence recovery of the VF.

Referring now to FIG. 4, as indicated in a block 400, the VF device becomes locked, provided at step or block 308 in FIG. 3. Then the VF device driver detects an error responsive to the VF device being locked, and commences an error recovery process or procedures as indicated in a block 402. As indicated in a block 404, the VF device driver polls the device state until the VF device is unlocked, which is provided at step or block 330 in FIG. 3.

As indicated in a block 406, the VF driver collects error data, if so indicated by the adapter driver, and logs the collected date appropriately. VF driver goes through normal reinitialization, and as part of reinitialization, it determines whether error data is to be collected with this indication provided at block 318 in FIG. 3 and is communicated from the adapter driver to the VF drivers. For example, this is accomplished via a VF driver query from the adapter itself of what the type of the last reset done to the adapter was. If the last reset was a firmware reset then error data is collected. The firmware reset is the indication that some other system component encountered an error that required the VF device driver to also collect its error data. The VF driver reads the EEH error data from the hypervisor. This includes a Log ID to allow correlation between the VF error data collected by each of the VF drivers, and also the error data collected by the adapter driver. The VF device driver completes recovery and resumes normal I/O operations as indicated in a block 408.

Referring now to FIG. 5, an article of manufacture or a computer program product 500 of the invention is illustrated. The computer program product 500 is tangibly embodied on a non-transitory computer readable storage medium that includes a recording medium 502, such as, a floppy disk, a high capacity read only memory in the form of an optically read compact disk or CD-ROM, a tape, or another similar computer program product. Recording medium 502 stores program means 504, 506, 508, and 510 on the medium 502 for carrying out the methods for implementing distributed debug data collection and analysis for an I/O adapter, such as a Single Root Input/Output Virtualization (SRIOV) adapter of a preferred embodiment in the system 100 of FIG. 1, or system 200 of FIG. 2.

A sequence of program instructions or a logical assembly of one or more interrelated modules defined by the recorded program means 505, 506, 508, and 510, direct the computer system 500 for implementing distributed debug data collection and analysis for an I/O adapter, such as a Single Root Input/Output Virtualization (SRIOV) adapter of a preferred embodiment.

While the present invention has been described with reference to the details of the embodiments of the invention shown in the drawing, these details are not intended to limit the scope of the invention as claimed in the appended claims. 

What is claimed is:
 1. A method for distributed debug data collection and analysis for an input/output (I/O) adapter in a computer system comprising: triggering a base error collection sequence responsive to a predetermined triggering event; collecting adapter driver data and locking out virtual function (VF) device drivers responsive to triggering the base error collection sequence; collecting adapter debug data and reinitializing the adapter including providing an indication to said VF device drivers if VF error data is to be collected; and unlocking the virtual function (VF) device drivers, allowing the VF device drivers to commence recovery of a respective virtual function (VF).
 2. The method as recited in claim 1, wherein the adapter includes a Single Root Input/Output Virtualization (SRIOV) adapter.
 3. The method as recited in claim 1, wherein the base error collection sequence includes collecting an adapter dump responsive to locking out said virtual function (VF) device drivers, the adapter dump including information on virtual functions (VFs).
 4. The method as recited in claim 1, wherein locking out said virtual function (VF) device drivers includes utilizing an error handling recovery function, and further includes collecting I/O host bridge debug data responsive to locking out said virtual function (VF) device drivers.
 5. The method as recited in claim 1, wherein said VF device driver detects an error responsive to the virtual function (VF) device drivers being locked, and commences an error handling recovery process; and further includes said VF device driver polling device state until the VF device is unlocked.
 6. The method as recited in claim 1, wherein said predetermined triggering event includes said VF device driver initiating an adapter dump on the adapter.
 7. The method as recited in claim 6, includes said VF device driver collecting error data responsive to said indication provided to said VF device driver of said VF error data to be collected.
 8. The method as recited in claim 1, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor receiving a request from a hardware management console (HMC).
 9. The method as recited in claim 1, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor detecting an internal adapter driver error.
 10. The method as recited in claim 1, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor detecting an adapter dump present on the adapter.
 11. The method as recited in claim 10, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor detecting one of an adapter error and a platform error.
 12. A system for implementing distributed debug data collection and analysis for a hardware I/O adapter in a computer system comprising: a processor; a hypervisor managing functions associated with the hardware I/O adapter; said processor using said hypervisor to perform the steps of: triggering a base error collection sequence responsive to a predetermined triggering event; collecting adapter driver data and locking out virtual function (VF) device drivers responsive to triggering the base error collection sequence; collecting adapter debug data and reinitializing the adapter including providing an indication to said VF device drivers if VF error data is to be collected; and unlocking the virtual function (VF) device drivers, allowing the VF device drivers to commence recovery of a respective virtual function (VF).
 13. The system as recited in claim 12, wherein the adapter includes a Single Root Input/Output Virtualization (SRIOV) adapter.
 14. The system as recited in claim 12, wherein the base error collection sequence includes collecting an adapter dump responsive to locking out said virtual function (VF) device drivers.
 15. The system as recited in claim 12, wherein locking out said virtual function (VF) device drivers includes utilizing an error handling recovery function, and further includes collecting I/O host bridge debug data responsive to locking out said virtual function (VF) device drivers.
 16. The system as recited in claim 12, wherein said VF device driver detects an error responsive to the virtual function (VF) device drivers being locked, and commences an error handling recovery process; and further includes said VF device driver polling device state until the VF device is unlocked.
 17. The system as recited in claim 16, includes said VF device driver collecting error data responsive to said indication provided to said VF device driver of said VF error data to be collected.
 18. The system as recited in claim 12, wherein said predetermined triggering event includes said VF device driver initiating an adapter dump on the adapter.
 19. The system as recited in claim 12, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor receiving a request from a hardware management console (HMC).
 20. The system as recited in claim 12, wherein said predetermined triggering event includes an adapter driver provided with a system hypervisor detecting one of an internal adapter driver error, a platform error, an adapter error, and an adapter dump present on the adapter. 